FHIR © HL7.org  |  Server Home  |  FHIR Server FHIR Server 3.4.11  |  FHIR Version n/a  User: [n/a]

Resource Requirements/FHIR Server from package hl7.ehrs.ehrsfmr21#current (31 ms)

Package hl7.ehrs.ehrsfmr21
Type Requirements
Id Id
FHIR Version R5
Source http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-CPS.9.2.2.html
Url http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.9.2.2
Version 2.1.0
Status active
Date 2024-11-26T16:30:50+00:00
Name CPS_9_2_2_Support_for_Provider_to_Professional_Communication
Title CPS.9.2.2 Support for Provider to Professional Communication (Function)
Experimental False
Realm uv
Authority hl7
Description Manage communications to professionals (e.g., coroners, medical examiners, law enforcement) for health care events.
Purpose Health care providers must be able to provide notifications and associated administrative, and/or clinical information to various professional individuals or organizations of specific health care events (e.g., patient deaths, births, gunshot wounds) in order to promote or trigger a workflow.

Resources that use this resource

No resources found


Resources that this resource uses

No resources found



Narrative

Note: links and images are rebased to the (stated) source

Statement N:

Manage communications to professionals (e.g., coroners, medical examiners, law enforcement) for health care events.

Description I:

Health care providers must be able to provide notifications and associated administrative, and/or clinical information to various professional individuals or organizations of specific health care events (e.g., patient deaths, births, gunshot wounds) in order to promote or trigger a workflow.

Criteria N:
CPS.9.2.2#01 dependent SHOULD

The system SHOULD provide the ability to determine, tag and present healthcare event records for notification to appropriate personnel or systems (e.g., events requiring notification to medical examiner, coroner, funeral director, law enforcement, vital records organizations), according to scope of practice, organizational policy, and/or jurisdictional law.

CPS.9.2.2#02 dependent MAY

The system MAY provide the ability to capture and store an indicator of death/fetal death notification to appropriate personnel or systems (e.g., medical examiner, coroner, funeral director, law enforcement, vital records organizations) including the date and time of the notification event, according to scope of practice, organizational policy, and/or jurisdictional law.

CPS.9.2.2#03 dependent MAY

The system MAY provide the ability to capture and store an indicator of birth notification to appropriate personnel or systems (e.g., general practitioner, vital records organization) including the date and time of the notification event, according to scope of practice, organizational policy, and/or jurisdictional law.

CPS.9.2.2#04 dependent MAY

The system MAY provide the ability to capture and render clinical details regarding birth, death and fetal death events to appropriate personnel or systems according to scope of practice, organizational policy, and/or jurisdictional law.

CPS.9.2.2#05 dependent MAY

The system MAY provide the ability to capture and render administrative details regarding birth, death and fetal death events to appropriate personnel or systems according to scope of practice, organizational policy, and/or jurisdictional law.


Source

{
  "resourceType" : "Requirements",
  "id" : "EHRSFMR2.1-CPS.9.2.2",
  "meta" : {
    "profile" : [
      "http://hl7.org/ehrs/StructureDefinition/FMFunction"
    ]
  },
  "text" : {
    "status" : "extensions",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Manage communications to professionals (e.g., coroners, medical examiners, law enforcement) for health care events.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>Health care providers must be able to provide notifications and associated administrative, and/or clinical information to various professional individuals or organizations of specific health care events (e.g., patient deaths, births, gunshot wounds) in order to promote or trigger a workflow.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2.2#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to determine, tag and present healthcare event records for notification to appropriate personnel or systems (e.g., events requiring notification to medical examiner, coroner, funeral director, law enforcement, vital records organizations), according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2.2#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to capture and store an indicator of death/fetal death notification to appropriate personnel or systems (e.g., medical examiner, coroner, funeral director, law enforcement, vital records organizations) including the date and time of the notification event, according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2.2#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to capture and store an indicator of birth notification to appropriate personnel or systems (e.g., general practitioner, vital records organization) including the date and time of the notification event, according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2.2#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to capture and render clinical details regarding birth, death and fetal death events to appropriate personnel or systems according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2.2#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to capture and render administrative details regarding birth, death and fetal death events to appropriate personnel or systems according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
  },
  "url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.9.2.2",
  "version" : "2.1.0",
  "name" : "CPS_9_2_2_Support_for_Provider_to_Professional_Communication",
  "title" : "CPS.9.2.2 Support for Provider to Professional Communication (Function)",
  "status" : "active",
  "date" : "2024-11-26T16:30:50+00:00",
  "publisher" : "EHR WG",
  "contact" : [
    {
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://www.hl7.org/Special/committees/ehr"
        }
      ]
    }
  ],
  "description" : "Manage communications to professionals (e.g., coroners, medical examiners, law enforcement) for health care events.",
  "jurisdiction" : [
    {
      "coding" : [
        {
          "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code" : "001",
          "display" : "World"
        }
      ]
    }
  ],
  "purpose" : "Health care providers must be able to provide notifications and associated administrative, and/or clinical information to various professional individuals or organizations of specific health care events (e.g., patient deaths, births, gunshot wounds) in order to promote or trigger a workflow.",
  "statement" : [
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : true
        }
      ],
      "key" : "EHRSFMR2.1-CPS.9.2.2-01",
      "label" : "CPS.9.2.2#01",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "The system SHOULD provide the ability to determine, tag and present healthcare event records for notification to appropriate personnel or systems (e.g., events requiring notification to medical examiner, coroner, funeral director, law enforcement, vital records organizations), according to scope of practice, organizational policy, and/or jurisdictional law."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : true
        }
      ],
      "key" : "EHRSFMR2.1-CPS.9.2.2-02",
      "label" : "CPS.9.2.2#02",
      "conformance" : [
        "MAY"
      ],
      "conditionality" : false,
      "requirement" : "The system MAY provide the ability to capture and store an indicator of death/fetal death notification to appropriate personnel or systems (e.g., medical examiner, coroner, funeral director, law enforcement, vital records organizations) including the date and time of the notification event, according to scope of practice, organizational policy, and/or jurisdictional law."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : true
        }
      ],
      "key" : "EHRSFMR2.1-CPS.9.2.2-03",
      "label" : "CPS.9.2.2#03",
      "conformance" : [
        "MAY"
      ],
      "conditionality" : false,
      "requirement" : "The system MAY provide the ability to capture and store an indicator of birth notification to appropriate personnel or systems (e.g., general practitioner, vital records organization) including the date and time of the notification event, according to scope of practice, organizational policy, and/or jurisdictional law."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : true
        }
      ],
      "key" : "EHRSFMR2.1-CPS.9.2.2-04",
      "label" : "CPS.9.2.2#04",
      "conformance" : [
        "MAY"
      ],
      "conditionality" : false,
      "requirement" : "The system MAY provide the ability to capture and render clinical details regarding birth, death and fetal death events to appropriate personnel or systems according to scope of practice, organizational policy, and/or jurisdictional law."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : true
        }
      ],
      "key" : "EHRSFMR2.1-CPS.9.2.2-05",
      "label" : "CPS.9.2.2#05",
      "conformance" : [
        "MAY"
      ],
      "conditionality" : false,
      "requirement" : "The system MAY provide the ability to capture and render administrative details regarding birth, death and fetal death events to appropriate personnel or systems according to scope of practice, organizational policy, and/or jurisdictional law."
    }
  ]
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.